home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Tools 5
/
Amiga Tools 5.iso
/
grafik
/
3d & render tools
/
irit
/
man
/
man6
/
setup.6
< prev
next >
Wrap
Text File
|
1996-07-16
|
7KB
|
162 lines
.TH Setup
6 "IRIT Version 6.0"
.SH NAME
Setup
The IRIT program reads a file called irit.cfg each time it is executed.
This file configures the system. It is a regular text file with comments, so
you can edit it and properly modify it for your environment.
This file is being searched for in the directory specified by the
IRIT_PATH environment variable.
For example 'setenv IRIT_PATH /u/gershon/irit/bin/'.
Note IRIT_PATH must terminate with '/'. If the variable is not set only
the current directory is being searched for irit.cfg.
In addition, if it exists, a file by the name of iritinit.irt will be
automatically executed before any other '.irt' file. This file may contain
any IRIT command. It is the proper place to put your predefined
functions and procedures if you have some.
This file will be searched much the same way IRIT.CFG is. The
name of this initialization file may be changed by setting the StartFile
entry in the configuration file.
This file is far more important starting at version 4.0, because of the new
function and procedure definition that has been added, and which is used
to emulate BEEP, VIEW, and INTERACT for example.
The solid modeler can be executed in text mode (see the .cfg and the -t
flag below) on virtually any system with a C compiler.
Under all systems the following environment variables must be set
and updated:
path Add to path the directory where IRIT's binaries are.
IRIT_PATH Directory with config., help and IRIT's binary files.
IRIT_DISPLAY The graphics driver program/options. Must be in path.
IRIT_BIN_IPC If set, uses binary Inter Process Communication.
For example,
set path = (path /u/gershon/irit/bin)
setenv IRIT_PATH /u/gershon/irit/bin/
setenv IRIT_DISPLAY "xgldrvs -s-"
setenv IRIT_BIN_IPC 1
to set /u/gershon/irit/bin as the binary directory and to use the sgi's
gl driver. If IRIT_DISPLAY is not set, the server (i.e., the IRIT
program) will prompt and wait for you to run a client (i.e., a display
driver). if IRIT_PATH is not set, none of the configuration files, nor
the help file will be found.
If IRIT_BIN_IPC is not set, text based IPC is used, which is far
slower. No real reason not to use IRIT_BIN_IPC, unless it does not
work for you.
In addition, the following optional environment variables may be set.
IRIT_MALLOC If set, apply dynamic memory consistency testing.
Programs will execute much slower in this mode.
IRIT_MALLOC_PTR Set to a pointer address and the program will
scream once this pointer is allocated.
IRIT_NO_SIGNALS If set, no signals are caught by IRIT.
IRIT_SERVER_HOST Internet Name of IRIT server (used by graphics driver).
IRIT_SERVER_PORT Used internally to the TCP socket number. Should not
be set by users.
For example,
setenv IRIT_MALLOC 1
setenv IRIT_MALLOC_PTR 1234567890
setenv IRIT_NO_SIGNALS 1
setenv IRIT_SERVER_HOST irit.cs.technion.ac.il
IRIT_MALLOC is useful for programmers, or when reporting a memory
fatal error occurrence. IRIT_NO_SIGNALS is also useful for debugging
when contorl-C is used within a debugger. The IRIT_SERVER_HOST/PORT
controls the server/client (IRIT/Display device) communication.
IRIT_SERVER_HOST and IRIT_SERVER_PORT are used in the unix and
Window NT ports of IRIT.
See the section on the graphics drivers for more details.
A session can be logged into a file as set via LogFile in the configuration
file. See also the LOGFILE command.
The following command line options are available:
IRIT [-t] [-z] [file.irt]
-t Puts IRIT into text mode. No graphics will be displayed and
the display commands will be ignored. Useful when one needs to
execute an irt file to create data on a tty device...
-z Prints usage message and current configuration/version
information.
file.irt A file to invoke directly instead of waiting to input from
stdin.
Under OS2 the IRIT_DISPLAY environment variable must be set (if set) to
os2drvs.exe without any option (-s- will be passed automatically).
os2drvs.exe must be in a directory that is in the PATH environment
variable. IRIT_BIN_IPC can be used to signal binary IPC which is faster.
Here is a complete example:
set IRIT_PATH=c:\irit\bin\
set IRIT_DISPLAY=os2drvs -s-
set IRIT_BIN_IPC=1
assuming the directory specified by IRIT_PATH holds the executables of
IRIT and is in PATH.
If IRIT_BIN_IPC is not set, text based IPC is used which is far
slower. No real reason not to use IRIT_BIN_IPC unless it does not
work for you.
The NT port uses sockets and is, in this respect, similar to the unix port.
The envirnoment variables IRIT_DISPLAY, IRIT_SERVER_HOST,
IRIT_BIN_IPC should all be set in a similar way to the Unix specific setup.
As a direct result, the server (IRIT) and the display device may be running
on different hosts. For example the server might be running on an NT system
while the display device will be running on an SGI4D exploiting the graphic's
hardware capabilities. Here is a complete example:
set IRIT_PATH=c:\irit\bin\
set IRIT_DISPLAY=wntgdrvs -s-
set IRIT_BIN_IPC=1
Under UNIX using X11 (x11drvs driver) add the following options to
your .Xdefaults. Most are self explanatory. The Trans attributes control
the transformation window, while the View attributes control the view window.
SubWin attributes control the subwindows within the Transformation window.
#if COLOR
irit*Trans*BackGround: NavyBlue
irit*Trans*BorderColor: Red
irit*Trans*BorderWidth: 3
irit*Trans*TextColor: Yellow
irit*Trans*SubWin*BackGround: DarkGreen
irit*Trans*SubWin*BorderColor: Magenta
irit*Trans*Geometry: =150x500+500+0
irit*Trans*CursorColor: Green
irit*View*BackGround: NavyBlue
irit*View*BorderColor: Red
irit*View*BorderWidth: 3
irit*View*Geometry: =500x500+0+0
irit*View*CursorColor: Red
irit*MaxColors: 15
#else
irit*Trans*Geometry: =150x500+500+0
irit*Trans*BackGround: Black
irit*View*Geometry: =500x500+0+0
irit*View*BackGround: Black
irit*MaxColors: 1
#endif